An inbound STOWPLAN EDI message, such as a BAPLIE message, describes a vessel visit and lists the containers arriving on the vessel and their location on the vessel, including the container number, equipment type, line operator, gross weight, and any seal numbers or hazardous information. The EDI message only contains information for one vessel visit.
When processing an inbound STOWPLAN EDI message, the following information must exist in N4:
Vessel visit
In addition, the vessel visit Lloyds ID or call number must exist in N4.
Port of load and port of discharge
Container number
Line operator
Equipment type (ISO code)
Stowage position
N4 checks if each container in the BAPLIE contains Stowage position (LOC+147 segment). If not, N4 stops processing in the classify stage itself and logs error message 'No LOC+147 segment found for the container <ICTR2012140 >' to indicate the LOC+147 is missing for the container.
If the ARGOBAPLIE004 (on page 1) setting is set to False for the selected EDI session, N4 uses the following posting logic to determine the category of the container based on the port of discharge.
If the port of discharge is equal to one of the following, N4 sets the category to Import:
The current facility's routing point
A sub-point in the vessel visit itinerary for current facility's routing point
If the port of discharge is not equal to the above and the EDI file specifies a transshipment port that is equal to the current facility's routing point, then N4 sets the category to Transship. Otherwise, N4 sets the category to Through.
You can set the Posting rule (on page 1) for Category property group for the STOWPLAN class. If the Existing Source is Dischargelist, then you can use the posting rule to Ignore the updates to the category. For example, in the Posting Rules view (on page 1), select the Stowplan group and set a posting rule for Category with the existing datasource as Discharge List EDI, and then ignore the update. After posting the COPRAR Discharge List EDI message with category as Import, when you set ARGOBAPLIE004 to True and then post the BAPLIE EDI message with category as Through, N4 retains the import the category since the COPRAR DISCHARGE exists for a unit.
If the ARGOBAPLIE004 setting is set to False and the EDI file specifies the transshipment port, for the posting logic to work correctly you may need to map the portid attribute in the transshipPort element in your mapping file to the segment in the EDI file that specifies the transshipment port.
When successful, N4 creates the units onboard the vessel specified in the BAPLIE file.
If a unit's port of discharge is not the current facility's routing point but is a sub-point of the facility's routing point in the vessel visit itinerary, and a facility relay exists from the current facility to the unit's port of discharge, then N4 updates the:
Category to import
Intended outbound carrier to a generic carrier, such as GEN_VESSEL or GEN_TRUCK, based on the Default Carrier Mode defined in the facility relay
Declared outbound carrier to GEN_TRUCK
If ARGOBAPLIE004 (on page 1) setting is set to True and you post an EDI BAPLIE with barge vessel, booking number, and container category set to EXPORT, N4 creates the unit with the following properties:
Category: Export (if the container POD that was posted in the EDI is the current port)
I/B Visit: The vessel visit obtained from the BAPLIE
O/B Visit: The booking's vessel visit
OPL: The POL obtained from the BAPLIE
POL: The current port terminal
POD: The booking's POD
In the mapping file, if N4 finds a SCAC and BIC code in the EDI file, N4 does not consider the line operator code. For example, the extracted XML has the below details in the container operator node:
<argo:containerOperator argo:operator="AAA">
<argo:organizationCodes argo:Id="XXX" argo:scacCode="XXX" argo:bicCode="XXX" />
</argo:containerOperator>
N4 first checks for the SCAC code in the mapping (.mgt) file. If the SCAC code is not available, N4 checks for the BIC code. If both codes are not available, N4 considers the operator value. Because the above example contains both the SCAC code and the BIC code, N4 does not consider the operator value. To test this, remove the SCAC code and BIC code for the line operator and then extract the BAPLIE file; N4 displays the operator value from the filter in the EDI file.